In the second week, we dove deeper into how the core techniques of e-signature actually work. Now, let’s do a quick review of this week’s journey.

Key Takeaway 1 : The PM as a "Technical Translator”

One of the key responsibilities of a PM is to act as a bridge between clients and engineers. This week, we learned how to read an API document, helping us feel more confident and grounded when answering questions from clients and engineers. We also walked through the full signing flow as a user, which helped us better empathize with their experience and pain points.

Key Takeaway 2 : The Anatomy of Digital Evidence

We discovered that an e-signature document is more than just a signature. It’s a comprehensive package of digital evidence, including :

• Audit Trail : Like a black box on an airplane, it records all critical data : who signed it, when, where, and every action taken.
• Timestamp : A trusted timestamp issued by Timestamp Authority (TSA), serving as an official seal to certify the time of signing.
• Packaging the Evidence : Finally, all of this information is embedded into a PDF file using standards like PAdES.

As PMs, understanding this structure helps us explain the value of digital signatures to clients and legal teams more effectively.

Key Takeaway 3 : The Skill of Verification

On Day 13, we explored the practical skill of verifying a digital signature using Adobe Acrobat Reader. We also touched a real-world challenge — how to explain to clients when the CA (Certification Authority) of your digital signature is not listed in Adobe’s trusted list, even though the signature itself is legally valid and technically sound, Adobe might still flag it as untrusted. As PMs, we need to help clients understand why that happens and reassure them about the signature’s authenticity.

This week equipped us with hands-on knowledge of how an e-signature process works. It helps PMs feel more confident and calm when communicating with both clients or engineers.

Next week, we’ll shift our focus to project management, from gathering requirements to handling unexpected changes. Stay tuned!

第一週我們建立了電子簽章的底層知識，了解了 Why 與 What，而剛剛完成的第二週，則是帶各位了解關於電子簽章技術的 How。

今天，就讓我們一起回顧這週的技術之旅吧！

第二週總整理

API 文件與簽署歷程

我們先以技術顧問 PM 的角度，學習如何看懂 API 文件，讓自己更有自信去回覆客戶的問題；接著，換成使用者的視角，以同理使用者的角度出發，親身體驗了一次簽署歷程。

數位證據與時戳

我們認識了稽核軌跡 (Audit Trail)，這個如同黑盒子般，紀錄了所有人事時地物的有力證據；並且了解到什麼是第三方認證的時戳 (Timestamp)，以及他的作用是用來確保時間的絕對準確性。

載體與鑑定方式

我們也學到，前面講到的那些數位證據的載體，是 PAdES 標準來規範的 PDF 檔案；並且學會了如何使用 Acrobat Reader 來確認一份電子簽章文件的真偽，還另外加碼了假如文件的 CA 並不在 Adobe 信任名單時，該如何回覆客戶，減輕疑慮。

至此，你已經是一個理解電子簽章核心技術的 PM 了！不用再擔心跟 RD 和客戶溝通時，有關技術的部份總是心驚膽跳，深怕被問倒。

但光懂技術和流程還不夠。下週，我們要進入 PM 的主戰場 — 專案管理。來探討如何從零開始啟動一個導入專案、進行需求訪談、規劃時程以及應對變動... ...等等的 PM 日常。